Skip to content

doc: Add pipeline guide#642

Draft
dionhaefner wants to merge 3 commits into
mainfrom
dion/pipeline-guide
Draft

doc: Add pipeline guide#642
dionhaefner wants to merge 3 commits into
mainfrom
dion/pipeline-guide

Conversation

@dionhaefner

Copy link
Copy Markdown
Contributor

Adds a guide on how to build Tesseract-driven pipelines. References cookiecutter-tesseract (not public yet), so don't merge before that's live.

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.03%. Comparing base (bf6887b) to head (9f6719f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #642   +/-   ##
=======================================
  Coverage   78.03%   78.03%           
=======================================
  Files          39       39           
  Lines        4685     4685           
  Branches      770      770           
=======================================
  Hits         3656     3656           
  Misses        720      720           
  Partials      309      309           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines +112 to +113

When a chain misbehaves, test each Tesseract in isolation first. A component you've verified on its own against a known input/output pair is a fixed point you can trust while debugging the workflow around it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a link to some docs on tesseract test or do you still feel this is too experimental.

The one thing that makes or breaks chaining is at the _interface_, not the call site: a step composes cleanly with the next only if its output fields line up with the downstream input schema. Design for that.

```{seealso}
[Designing good interfaces](design-patterns.md#designing-good-interfaces) — matching one Tesseract's `OutputSchema` to the next's `InputSchema` is what keeps chains readable. Design interfaces with the downstream consumer in mind.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm not so keen on this, it feel a bit strong and prefer certain design patterns unnecessarily. The example above breaks this pattern (outputs from one Tesseract are used in another but that's it, the name changes, you still have to extract it, etc.

Comment on lines +125 to +128
```bash
$ pip install cookiecutter
$ cookiecutter github:pasteurlabs/cookiecutter-tesseract
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we give uv installation instruction as well/instead (see https://github.com/cookiecutter/cookiecutter)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants